Systems and methods for converting and delivering medical images to mobile devices and remote communications systems

ABSTRACT

Systems and methods are provided for automated conversion of medical images and delivery to mobile devices or remote communication systems. Medical images are stored, along with related metadata, at a central location such as a server in a medical data format. A user can then submit a request or query to find the medical images on the server and deliver them to a mobile device or other remote communication system separate from the central location. The medical images are then converted to a standardized format specification based on an output destination type of the mobile device or remote communication system. A message is assembled with the converted medical data from a message template and is then transmitted to the mobile device or remote communication system.

RELATED APPLICATIONS INFORMATION

This application claims priority under 35 U.S.C. 119(e) to U.S.Provisional Patent Application Ser. No. 61/251,334, filed Oct. 14, 2009,and entitled “Converting and Delivering Medical Images to Mobile Devicesand Remote Communication Systems,” which is incorporated herein byreference in its entirety as if set forth in full.

BACKGROUND

1. Technical Field

The embodiments described herein are related to delivery of medicalimage records, and more particularly to the automatic conversion ofmedical image file for delivery to mobile devices and/or remotecommunication systems.

2. Related Art

Medical diagnostic devices and medical imaging systems have becomeincreasingly complex in recent years. In response to the increasingchallenges in digital imaging technology, the American College ofRadiology (ACR) and the National Electrical Manufacturers Association(NEMA) developed the Digital Imaging and Communications in Medicine(DICOM) standard. DICOM is a standard for handling, storing, printing,and transmitting information in medical imaging. It includes a fileformat definition and a network communication protocol. The networkcommunication protocol is an application protocol that uses TCP/IP tocommunicate between systems. One of the goals of the standard is to makeuniform the transferring of medical images and information betweenviewing and scanning sources to allow users of different imagingsoftware and/or hardware to share information. DICOM files can beexchanged between two entities that are capable of receiving image andpatient data in DICOM format. DICOM enables the integration of scanners,servers, workstations, printers, and network hardware from multiplemanufacturers into a Picture Archiving and Communication System (PACS)for storing and downloading of digital images. The different devicescome with DICOM conformance statements that clearly state the DICOMclasses they support. DICOM has been widely adopted by hospitals, and isgaining popularity in smaller dentists' and doctors' offices.

DICOM files commonly contain images; therefore, they are often referredto as DICOM images. But it will be understood that a DICOM file does notnecessarily need to include an image. Rather, such a file can includemeasurements or report data. Thus, DICOM files may contain media data,such as, video and audio data, or no media data at all. In that case,DICOM files may contain only metadata identifying the originatingmodality, the operator, or the patient being examined. Modality hererefers to any image generating equipment in medical imaging, such as,Ultrasound (US), Magnetic Resonance Imaging (MRI), Computed Tomography(CT), Positron Emission Tomography (PET), radiographs, and the like.

The type of data and amount of data available in any one DICOM imagefile varies. A DICOM file is generally structured using data identifyingPatient, Study, Series and Instance in that hierarchical order. APatient can be involved in a number of Studies (cases), which in turnmay contain a number of Series (examination or visits), which in turnmay contain a number of Instances (files usually containing images). Itmeans that a DICOM file can be unambiguously identified and fitted intothat hierarchy. All DICOM files contain an identifier for the generatingmodality. In other words, the identifier will reflect the equipment orlocation in which the file was originated. The files also containtimestamps pertaining to both the file itself (Instance) and the Series.Using the timestamps and the originating identifier, an image can beunambiguously identified using that data without involving anyidentifiable patient information to safeguard patient privacy issues. Inaddition, DICOM file format differs from other data formats in that itgroups information into data sets. For example, a file of a chest X-Rayimage actually contains the patient ID within the file, so that theimage can never be separated from this information by mistake.

Most PACSs handle images from various medical imaging instruments,including US, MRI, PET, CT, and the like. Electronic images and reportsare transmitted digitally via PACS; this eliminates the need to manuallyfile, retrieve or transport film jackets. A PACS consists of four majorcomponents: the imaging modalities, such as, CT and MRI; a securednetwork for the transmission of patient information; workstations forinterpreting and reviewing images; and long and short term archives forthe storage and retrieval of images and reports. Combined with availableand emerging Web technology, PACS has the ability to deliver timely andefficient access to images, interpretations and related data. PACSbreaks down the physical and time barriers associated with traditionalfilm-based image retrieval, distribution and display.

Medical imaging devices typically output digital image data. Theoverwhelming majority, if not all, of such devices use the DICOMstandard for both image file format and network transfers. These imagesare generally not readable by consumer image viewers or mobile devices.Therefore, patients who wish to share their medical images struggle withconversion and delivery of these images. A good example is to shareimages from an Ultrasound examination during a pregnancy. The futureparents usually would like to keep, share and display the images oftheir future child. They might also conceivably want to send theseimages to their friends' and relatives' cellular phones or emailaccounts. They might even want to post them on a social network, or theymight just want to keep them in their personal digital “photo album”.All of these events would require them to either scan a printedhard-copy of the image, or to find, purchase, install and learn to useDICOM viewer software package with export capabilities. These softwarepackages are usually not readily available or they are not economicalfor limited use.

It should also be noted that this issue is not necessarily limited toDICOM files. In general, there is no real method for a patient to viewimages related to their condition, treatment, status, etc. Moreover,there are few, if any effective means by which a doctor or clinician canquickly and remotely retrieve images for diagnostic or other purposes.

In fact, many smaller medical practices, such as, small clinics,doctors' offices, and dentists' offices also suffer from an inability toconvert, deliver, and receive medical images economically and timely.These facilities usually do not have the technical support-staff orfinances to run a full PACS for image archiving and delivery to remoteexpert doctors for second opinions and consultations. They often resortto using films, or writable CDs which are sent by mail or messenger.This is both slow, environmentally unfriendly and, in the case of usingunregistered postal delivery, insecure. The cost of running a PACS isnot just paying the licensing fees. Major investments in advancedinfrastructure including the surrounding software, hardware, andfacility, as well as the cost for educating staff, and the hours spenton administration will add to the cost of running a PACS. These majorinvestments are expensive, therefore, usually out-of-reach for mostsmall businesses.

SUMMARY

Systems and methods for the quick and easy distribution of medicalimages to a plurality of output modalities in a manner that maintainsthe highest possible image quality and resolution are described herein.

According to one aspect, a system for automated conversion and deliveryof medical images, comprising: a communication interface; a userinterface; a data storage system configured to store a plurality ofmedical images, meta data associated with the plurality of medicalimages, converted medical images, a plurality of standardized formatspecifications for a plurality of destination devices and services, anda plurality of message templates; a server coupled with the data storagesystem and the communication interface, the server configured to:receive a plurality of medical image files via the communicationsinterface, the medical image files comprising medical data and metadata, the medical data having a medical data format, store the medicalimage files, receive a request via the user interface to find a medicalimage file, return a notification that the requested medical image filehas been found via the user interface, receive an output destinationtype associated with the medical data file via the user interface,wherein the output destination type is an output device, service, orboth, retrieve the requested medical image file, determine whether themedical data associated with the requested medical image file includesmedical image data, correlate the output destination type with one ormore of the plurality of standardized format specifications and with oneor more of the plurality of message templates, convert the medical dataformat associated with the medical data based on the standardized formatspecifications that correlate with the output destination type, assembleat least one output message that includes the converted medical databased on the message templates that correlate with the outputdestination type, and transmit the output message to at least onedestination via the communication interface.

These and other features, aspects, and embodiments are described belowin the section entitled “Detailed Description.”

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and embodiments are described in conjunction with theattached drawings, in which:

FIG. 1 is a diagram illustrating an example system for the automaticconversion and distribution of medical images to any of a plurality ofoutput modalities in accordance with one embodiment;

FIG. 2 is a high level block diagram illustrating certain components ofan example data conversion and delivery system that can be included inthe system of FIG. 1 in accordance with one embodiment;

FIG. 3 is a flow chart illustrating an example automated messagecreation process performed by the data conversion and delivery system ofFIG. 2 in accordance with one embodiment;

FIG. 4 is a flow chart illustrating example type of information and datathat can be examined in the process of FIG. 3 in accordance with oneembodiment;

FIG. 5 is a flow chart illustrating an example process for the use ofinformation embedded inside of the metadata included with incoming filesby the data conversion and delivery system of FIG. 2 in accordance withone embodiment;

FIG. 6 is a flow chart that illustrates the operation of an imageconverter module that can be included in the data conversion anddelivery system of FIG. 2;

FIG. 7 is a flow chart illustrating a typical use of a Web GUI that canbe included in the data conversion and delivery system of FIG. 2 and itsstreamlined interface for finding an image by the originating modalitywithout any identifiable patient information in accordance with oneembodiment;

FIG. 8 is a flow chart illustrating a variation of the typical use ofthe Web GUI and its streamlined interface for finding an image by usinga piece of identifiable patient data in accordance with one embodiment;and

FIG. 9 is a diagram illustrating an example system for the automaticconversion and distribution of medical images to any of a plurality ofoutput modalities in accordance with another embodiment.

DETAILED DESCRIPTION

FIG. 1 is a diagram illustrating an example system 100 for the automaticconversion and distribution of medical images to any of a plurality ofoutput modalities. The term output modality is used to refer to varioustypes of devices, systems, and services, several examples of which areprovided below. As can be seen, system 100 can comprise a plurality ofsource medical imaging modalities 10, such as Ultrasound, MRI, CT andPET equipment, a local PACS 20 (typically source image archive-servers),or any other device capable of sending medical data such as DICOM data,commonly medical images. Modalities 10 and PACS 20 can be connected,e.g., with a Central Computer System (CCS) 30 via the Internet 60through a router 50 usually provided with encryption and firewallprotection.

Central Computer System (CCS) 30 can include a data conversion anddelivery system (DCDS) 32 for processing the medical data. The CCS cancomprise one or more servers, and include one or more a processors orCPUs, memory associated with the processor(s), a data storage module, adisplay means, and an input/output interface means. It should beappreciated that various other peripheral devices and modules can beconnected to the CCS, such as other servers, other data storage modules,or intrusion detection systems. The CCS can also be a cluster ofinteroperating servers, each taking care of a specific task within thesystem. Similarly, all the modules shown in FIG. 2, and described belowcan each be a separate server in such a cluster, so as to distribute theload and increase the capacity of the system.

DCDS 32 can be configured to convert medical images associated with themedical data into, e.g., consumer-friendly images, video, or both. DCDS32 can then in turn send these converted images to a number ofdestinations, or output modalities 40 as directed by the user/operatorof DCDS 32 or as dictated by information included in the medical data.These destinations 40 can be, for example, a web site such as a socialnetworking site including, e.g., Twitter, Facebook, and Google Health;cellular phones; PDAs; Email accounts; or any computer system capable ofaccepting data via protocols such as, e.g., SOAP and REST. DCDS 32functions in such a way that it allows source modalities (10, 20) to beprotected by the most rigorous of firewall settings 50, while stillallowing transfers to take place over the internet 60. The originalsource image data may optionally be sent to the destinations 40 withoutany processing or conversion.

For example, when a patient undergoes an ultrasound examination duringpregnancy, the ultrasound images can be sent to DCDS 32 for conversioninto a set of images that can be sent the parent's social networking webpage, their mobile device, their friends and families devices or webpages, etc. More specifically, a nice sequence of the fetus waving itsarm can be captured and stored during the ultrasound examination by theoperator. The ultrasound operator, usually a nurse or technician, sendsthe stored, e.g., DICOM file to DCDS 32. The nurse, technician or anytrusted employee at the patient's facility (user) can use a remotegraphical user interface (GUI) interfaced with DCDS 32 to bring up thedesired sequence sent by the source modality 10. The user can then enterthe cellular phone numbers, web account information, email addresses,etc., as well as any personal message that the patient indicates, andthen start the delivery process. The, e.g., DICOM file, now convertedinto a cellular phone compatible video format, e.g., 3gpp, can then besent as a multimedia message to the mobile phones, and files convertedto other appropriate formats can also be sent to the given email and webaccounts.

Alternatively, the nurse or technician at the patient's facility canenter the patient's cellular phone number in the patient informationfield on the ultrasound machine. On receiving the, e.g., DICOM datafile, DCDS 32 can be configured to then locate that number embedded inthe DICOM data file, and automatically forward the converted image orvideo file after processing to the desired locations as specified by thepatient. Examples of these processes are described in detail below.

FIG. 2 is a high level block diagram illustrating certain components ofan example DCDS 32 in accordance with one embodiment. It will beunderstood that the diagram of FIG. 2 is for purposes of explanation andillustration and is not intended to restrict the embodiments describedherein to any particular architecture or design. Nor is FIG. 2 intendedto provide a detail view of all components of an example DCDS 32. Inoperation, a request from a modality 10 can be handled by an inputstage, consisting of a Receiver 203 and Storage & Parser 204. TheReceiver 203 can be configured to authenticate the connection from thesource modality 10, and to handle the network transactions necessary tocomplete the request.

Storage & Parser 204 can be configured to parse the received data and tostore any image data 205 and all metadata 206 in storage system 214. Forexample, the image data 205 can be stored as binary data, while themetadata can be stored as structured data allowing typical structuredaccess to the data, such as, searches and associations between differentitems. Storage & Parser 204 can be configured in certain implementationsor under certain conditions to strip all sensitive patient informationfrom the incoming data file. For example, an operator of the system canuse a Graphical User Interface (GUI), such as a Web GUI 208 toselectively set the parts of metadata that are considered to besensitive. Alternatively, the system can be programmed to automaticallydetermine which fields in the meta data are sensitive. This process iscalled anonymization, and it is performed in order to protect thepatient's privacy. Anonymization is discussed in more detail below.

In certain embodiments, an event signal can be triggered indicating thatthe newly stored data has been added. When Event System module 209receives an event signal from the parser 204, it can be configured todetermine what action, if any, should be taken as a result. For example,if rules for automatic delivery have been set, and the appropriatemetadata values are found in the newly received data stored instructured database 206, then Event System module 209 can be configuredto signal the Output Module 213 to send the converted data as instructedby the automatic delivery rules. This process is also described in moredetail below.

Output Module 213 can be configured to accept calls from other parts ofDCDS 32 containing general data, information to send, and number ofdelivery destinations, including email addresses. For example, the datacan include a text message, a reference to a, e.g., DICOM image, twocellular phone numbers, and one email address. The Output Module 213 canbe configured to assemble the appropriate formatted output “packages”,or messages, and send the resulting messages using a modularplug-in-based architecture. A plug-in (not shown) for each correspondingtype of destination can be included and used by Output Module 213.

In the example provided above, when a service call is received by DCDS32, Output Module 213 can assemble one MMS message packet containing ajpeg version of an image and message text, all combined and encodedaccording to the MMS specifications. This message can then be senttwice, first to each phone number destinations requested, and secondly,to each email address destinations specified.

Output Module 213 can request a converted image from Image Converter211, identifying the original image and specifying the requested formatand dimensions. Image Converter 211 can be configured to then look foran existing image in the Converted Image Cache 212 that matches therequest. If no match is found, it can generate an image from theoriginal image data 205. The Image Converter 211 can be configured touse the metadata 206 of the original image stored in database todetermine if the requested format is appropriate. If not, it can respondwith an error. For example, requesting an mp3 audio version of a stillimage would result in an error, while requesting a jpeg still image of amulti-frame DICOM image file (effectively video) would be proper.

Image Converter 211 can be configured to respond to an event from Parser204 and perform common conversions preemptively. This will improve theresponsiveness of the system components, in particular, the OutputModule 213 and the Web GUI 208; however, the trade-off is an increase instorage required, and also a slight decrease in the overall securitylevel.

A Web GUI 208 provides, e.g., medical staff with remote access to DCDS32 via a secured web browser connection (https) 202. Such a Web GUI 208can provide an interface to perform administrative tasks such as settingup rules for Event System module 209, as well as an optimized interfacefor identifying images and sending output messages. The typicaloperations of these interfaces are described in detail below.

Web GUI 208 can operate on the structured metadata 206 to find andidentify images. It can be configured to request conversions from ImageConverter 211 to, e.g., display thumbnails and previews of images, andto provide service request forms where output messages can be specifiedand send on to Output Module 213 for delivery.

An adaptable Garbage Collector 207 can continually evaluate the state ofall data and compare that to configurations made by an administrator ofthe system. The configuration can set certain criteria that items needto meet in order to remain in the system or be deleted from the system.One basic criterion can be the age of an item. For example, if an itemhas been stored over a week ago or certain number of days ago could beautomatically deleted. Other automatic deletion criteria can be thenumber of times an item has been previously sent, system stateinformation stored, and the value of any metadata. This feature is inpart useful for keeping the resource usage down, and also to aid patientconfidentiality by removing patent data that the system is no longerneeded to maintain.

It should be noted that in some embodiments the images are to be usedfor clinical or diagnostic purposes. In such instances, it is oftenrequired that the image that is ultimately displayed on the device usedfor viewing the images maintain a certain resolution or image quality.As such, in certain embodiments, one or more of Parser 204, Event Systemmodule 209, and Image Converter 211 can be configured, either alone orin combination, to recognize that the image is being viewed in adiagnostic or clinical application. Such recognition can be based oninformation included in the meta data, information stored in ImageSystem 214, or information provided via GUI 208.

For example, the address or device identified in the meta data forreceiving the image can be recognizable as an address or deviceassociated with a clinical or diagnostic application, the image orseries identifier can also be associated with a clinical or diagnosticapplication, etc. Alternatively, an operator can indicate through GUI208 that images to be sent are intended for clinical or diagnosticpurposes.

When it is determined that the images are to be used for clinical ordiagnostic purposes, then Image Converter 211 can be configured todetermine, e.g., based on information stored in storage system 214, therequired resolution or image quality. For example, resolution, imagequality, or both for various types of images, clinical applications,etc., can be stored in storage system 214. Image converter can thendetermine the correct image resolution and quality and covert the imagein accordance therewith. In certain embodiments, DCDS 32 can beconfigured to determine whether the identified output device or addressis capable of displaying the converted image with the requisite imageresolution and quality before sending the image. If the device oraddress is not capable, then DCDS can generate an error message or othernotification indicating such. The error message can be displayed throughGUI 208, on the device, or both.

As noted above, DCDS 32 can be configured to take an incoming medicalimage file and automatically convert it for distribution to and viewingby any of a plurality of output modalities. FIG. 3 is a flow chartillustrating one example embodiment for an automated message creationoperation performed by DCDS 32 in accordance with one embodiment. In theexample of FIG. 3, it is assumed that destination information, e.g.,output modality information is included in a medical image file receivedby DCDS 32. In other embodiments, a user can access DCDS 32, e.g.,through GUI 208 and specify which files should be sent to which outputmodalities; however, a powerful aspect of DCDS 32, as configured inaccordance with the systems and methods described herein, is its abilityto automatically determine the destinations and to convert and formatthe data appropriately as described below.

In step 320, a file is received and the headers associated therewith areexamined to determine various information. The medical image filereceived by input 203 will often include metadata that providesinformation related to the medical data or images included therewith.For example, in a DICOM file, the medical image file will include aheader that comprises a plurality of fields. These fields are generallythe same for each input modality 10. Thus, DCDS 32 can be configured toexamine the header fields to determine various information as describedin detail below and with respect to FIG. 4.

In step 322, an output destination type, or modality can be determined.For example, the header can include information identifying recipientsof the images included in the image file. Or more specifically, theheader can include information identifying output modalities associatedwith various recipients or services, e.g., such as an online photo albumpage, site, or service; a social networking page or service, a mobiledevice, etc. Basic types of destinations can include a mobile device,such as a cellphone; an email account; a Web-Application SpecificInterface (API), e.g., associated with an online site or service, etc.Thus, DCDS 32 can be configured to examine the header file and determineassociated output devices or services, i.e., modalities.

Whenever possible, DCDS 32 can be configured to then retrieve specificcharacteristics of each destination type as indicated in step 324. Thesecharacteristics can include capabilities and physical characteristics ofthe destination device and specifications and limitations of the networkclass and message type. This information is then used to determine theoutput formatting and other specifications needed for each outputmodality. For example, this information can be used for adaptations ofthe image data based on specifications for the type of message beingsent, e.g., e-mail has limitations in specification and common practicethat can be adapted for; and MMS has very different limitations that canbe adapt for.

The capabilities and characteristics determined in step 324 can includeframe size, i.e., pixel dimensions of an image or video, e.g., 640 by480 and the like; data rate or data size, e.g., MMS messages cancommonly not exceed 300 KB total size, e-mail attachments exceeding 10MB are often not accepted, etc.; supported encoding format, e.g. mpeg 4,jpeg, etc.; and message layout rules, i.e., how a message can becomposed for the destination, e.g. MMS is made of “pages”, each able todisplay a single image or video and a single text along with playingaudio while e-mail is capable of HTML layouts and can hold attachmentsof any file type, etc.

In step 326, a basic compatibility check can be performed to determinewhether the data included in the image file can be delivered in a formatcompatible with the output modality. For example, if the image dataincludes video data, then a determination can be made as to whether theoutput modality is capable of receiving and displaying video data.

The most suitable delivery format is then chosen in step 328 to ensurethe output message that is ultimately generated includes the bestquality data that the output modality can handle. This can be importantfor example in clinical settings or settings where the data is beingused for examination or diagnostic purposes. Resolution informationsuitable for diagnostic purposes and the ability of DCDS 32 to providesuch resolution is discussed in detail below.

Then, in step 330 the data can be extracted and converted as required.For example, MMS messages allow only a very limited total message size.Therefore images or video in particular often need to be adapted andoptimized to let the final message meet the format and specificationrequirements of a particular output modality. In contrast, e-mailmessages often have no strict limit on size and therefore can acceptlarger files, e.g., higher resolution images or video. But even e-mailaccounts can include rules limiting extremely large files and thereforeeven e-mail messages can require optimization of, e.g., video files toensure sufficient quality but also to comply with size limitations.

If the incoming file is already encoded in a format compatible with theoutput modality, then often no conversion will occur in step 330 inorder to preserve the highest possible image quality.

In step 332, the data can be anonymized as required by any applicableanonymization rules. For example, the data can be extracted and copiedinto a generic format so that certain data can be removed, redacted,etc. The data can then be converted to the final output format. Steps330 and 332 can be performed in parallel or reverse order as required bya particular implementation.

In step 334, the converted data can then be assembled into an outputmessage in accordance with the applicable formats and specificationsdetermined in the preceding steps. Optionally, other data can beincluded with the message. This information can be manually entered,e.g., via GUI 208 or it can be extracted from the metadata accompanyingthe received file. Still further, the data can be data retrieved fromconfiguration settings based on the set of characteristics describedabove.

In certain embodiments, the data components that are to comprise anoutput message are assembled according to template rules for the type ofmessage being created. For example, the various template rules can bestored in Storage System 214 and accessed by Output Module 213 in orderto assemble the output message. For example, MMS messages are based on apage metaphor where each page can contain an image or video, a textelement, and an audio element. Thus, sending two or more images, orincluding text, audio, or both with the image(s) will then require themessage to be assembled into several pages. By contrast, e-mail messagescan include any number of images, attachments, etc., depending on, e.g.,the message size restrictions.

Output Module 213 can then be configured to elect the appropriate outputgateway for transmission of the assembled output message in step 336.For example, Output Module 213 can be configured to send an e-mailmessage to a SMTP server (not shown) and to send an MMS message to a MMSgateway (not shown).

FIG. 4 is a flow chart illustrating example type of information and datathat can be examined in step 320. As can be seen in FIG. 4, when thefile comes in, the metadata or more specifically the header can beexamined to identify the input modality in step 420. In step 422, thecompatibility of the modality determined in step 420 with the system canbe determined. If compatible, then in step 424, specific characteristicsof the data included in the image file can be determined. For example,whether or not the file actually includes any image or video data orwhether the data is simply report or measurement can be determined instep 424. When an incoming file does include, e.g., report ormeasurement data, then such information can be extracted and stored in,e.g., a generic structured format in step 426. In step 428, any imagedata can then be extracted and stored as well and variouscharacteristics can be determined such as binary encoding format, framesize, color bit depth, still image or video, etc.

FIG. 5 is a flow chart illustrating an example process for the use ofinformation embedded inside of the metadata including with incomingfiles by DCDS 32 in accordance with one embodiment. The metadata, e.g.,header fields can be used to ensure safe and secure delivery of theimage data included therewith. For example, a DICOM image file caninclude a plurality of header fields that are key-value pairs in anumber of datatypes, such as strings, numbers, dates, specialmeasurement types, etc. Fields can be embedded in the and can be hardlinked to the file for which the provide metadata. In this way, there isno way to mix-up header files and the associated data, since they arenot separated.

In step 520, DCDS 32 can be configured to automatically track and recordheader fields for each network device sending images. In this way, DCDS32 can identify the specific device associated with an incoming file.DCDS 32 can do this by recording which header fields are present for aparticular modality 10 in step 522 and to then record the data includedin device-dependent header fields for the associated modality in step524. A particular device should always report the same values for, e.g.,manufacturer, model name, model number, etc. Thus, DCDS 32 can use thisinformation to identify a particular device.

In step 526, DCDS can detect any changes in the data and then takeappropriate action. For example, changes to header field data thatshould not be changed, e.g., manufacturer information, can be anindication that the file has been tampered with or someone is trying tohack into the system. In response to detection of such changes, thesystem can log the event, notify an operator, place the incoming data inan approval queue, quarantine the data or any further data from theassociated device, reject the data, rejecting the all future data fromthe device, to name just a few possible actions.

In step 528, DCDS can be configured to search the header fields for datathat can identify an intended recipient as noted above. Identificationcan be in the form of an actual, e.g., e-mail address, mobile stationInternational Subscriber Directory Number (ISDN), web site address, etc.In fact, such direct identification can be preferable as it takesadvantage of the existence of the header fields. Identification can alsobe indirect such as an ID that can be used to look up a direct address,e.g., in a registry stored in storage system 214. It should also benoted that each field can include more than one piece of data and dataof different types. Accordingly, any identifying or address fields caninclude telephone numbers as well as e-mail address, etc. Further,identifying data can be included in more than one field.

The DCDS 32 can be configured to then determine an action to take instep 528 based on any identifying data detected in step 530. Suchactions can include sending an appropriate message to any addressesfound, formatting messages appropriately as described above, notifyingan operator, adding a message to a queue, e.g., for manual approval,locating and adding other data or information to an outgoing message, toname just a few.

Accordingly, FIG. 6 is a flow chart that illustrates the operation ofDCDS 32 in more detail. Referring to FIG. 6, a Conversion Request 301can be received containing, at a minimum, an internal identifier for theimage, and a destination format. As noted above, the conversion requestcan be the result of information and data included in the metadataassociated with an incoming file. As noted below, however, the requestcan also result from input received through GUI 208. Optionally, therequest could contain new image dimensions to be scaled as output imageto be sent. The Image Converter 211 can be configured to then determinethe existence of the requested image 304 by trying to locate themetadata associated with it in metadata database 303. If no recordexists for the requested image, the converter can optionally return aplaceholder image (305, 308) or abort the conversion attempt 306. Aplaceholder is typically an image, video or similar media communicatingthat the requested image is unavailable. At this point, the converteralso can also be configured to determine if the requested output formatis feasible or not.

If a metadata record in database 303 does exist, then the converter canbe configured to load the, e.g., DICOM image 307 from image storage 302into a raw binary format. The Converter 211 can be configured to thendetermine if the image data should be resized to the dimensions providedin the request or to the dimensions required by the requested outputformat. For example a jpeg preview for the Web GUI 208 could be renderedin any dimensions that are suitable to the layout of the html document,while video for MMS messages have very specific dimensions to complywith the specification.

Next, the image data can be converted 311 to the requested destinationformat. The results can be saved to an image cache 312 and metadatarecords can be updated 313 to indicate the existence of the convertedimage. Finally, the converted images can be returned as a response tothe request. Converter 211 can then return either the converted binarydata directly or return a reference to its location in the image cache313.

As noted, DCDS 32 can also be operated and interfaced with through theWeb GUI 208. GUI 208 can enable both remote and local access the DCDS 32and allows for images to be located within storage system 208. Theimages may need to be located or analysis or diagnosis or for sending toa specified destination or address.

Two primary ways for accessing files can be provided. The first wayinvolves finding files without any identifying information. This isexplained in detail with respect to FIG. 7; however, it should first benoted that each device sending files to DCDS 32 can be identified byrecording and mapping header fields of incoming file transfers. Thedevices can also be at least partially identified based on their networkaddress, AE titles used for the transfer, or both. Each device can thenbe given a name that is unique and preferable meaningful to operators.Files as well as their series, study, or both, can then be identified bythe device they originated from, the time and date of the image capture,and header fields identifying the operator of the device used to capturethe images.

Since no patient information is needed, DCDS 32 can handle anonymizeddata and no patient information can be gathered by the misuse of thesystem. Further, the most used images can be stored as the most recentimages in the system. Thus, finding images can be made very efficient inthis manner. Once the file, series, study, etc., had been found, GUI 208can offer the operator direct access to features for viewing the images,sending the images, etc.

With this in mind, FIG. 7 is a flow chart illustrating a typical use ofthe Web GUI 208 and its streamlined interface for finding an image bythe originating modality without any identifiable patient information(401-404) in accordance with one embodiment. When an image has beenidentified (405,) the interface displays a service request form wherethe user enters output destination information and other messagedetails. If the data validates (407,) the required conversions arerequested (408) from the Image Converter (211.) For all successfulrequests, the data is assembled by the appropriate output plug-ins(409-411,) and the results are sent (412-414) to the appropriatedestinations. Status information for each individual output is gathered(415,) and returned (416 or 417) to the form view (405) for display. Atthis point, the user can choose to repeat the send process or return tofinding another image.

The Web GUI 208 allows for sending groups of images that belong to thesame, e.g., DICOM Series. The operating steps are similar to thoseillustrated by FIGS. 7 and 8. The Web GUI 208 also present interfacesfor configuring the Event System 209, organizing and storing outputdestination addresses and other administrative tasks necessary. It isimportant to note that, as a security measure, the Web GUI 208 does nothandle any authorization of source modalities allowed to store images oraccess privileges to those images. These important settings are onlyavailable through a separate method of access either locally orremotely. With the DCDS running on a Unix-style operating system, remoteaccess would typically be via the Secure Shell (SSH) protocol. If theDCDS is running on a Windows operating system, remote access wouldtypically be via Terminal Services. Both protocols are examples ofsecured remote access to the operating system.

The second way to access files is to use identifying information. Forexample, operators can search for files using patient information suchas name, birth date, patient ID, etc. The operator can, for example,input a search term and if there is a match, the system can present allavailable studies. If multiple patients are returned, then they can bepresented for selection. Once the patient is selected, and theassociated file, series, study, etc., had been found, GUI 208 can offerthe operator direct access to features for viewing the images, sendingthe images, etc.

FIG. 8 is a flow chart illustrating a variation of the typical use ofthe Web GUI 208 and its streamlined interface for finding an image byusing a piece of identifiable patient data (501-504,) such as, patientname, and birth-date, etc. Alternatively, any unrelated identifyingpassword or PIN code can be utilized to avoid using real patientinformation to ensure patient privacy. After that, the processing stepsas described above related to FIG. 7 can be followed.

In certain embodiments, CCS 30 can be interfaced with a server 902 thatcan be configured to host and support various value added services for,e.g., patients and family in relation to the images being captured bymodalities 10 as illustrated in FIG. 9. For example, if the images arefetal ultrasound images, the server 902 can be configured to provide avariety of services for the parents, family, friends, etc. For example,the DCDS 32 can be configured to convert the images to a proper formator formats supported by server 902 and the related services. The imagescan be sent to server 902 and stored in storage system 904.

It will be understood that server 902 can actually comprise a pluralityof servers, computers, routers, etc., as well as the appropriatesoftware and firmware required to carry out the functions describedherein. Further, storage system 904 can comprise one or more databases,one or more storage servers, as well as other physical storage mediumsas required.

Server 902 can then be configured for example, to host a web site onwhich users can create accounts. The users can then access the images onthe site and purchase images, pregnancy calendars, customized mugs, keychains, T-shirts, canvases, etc. Further, the site can be configure topresent pictures, illustrations, information on fetus and childdevelopment, health and nutrition tips, etc. Such a site can enable suchservices as a registry, e.g., for a baby shower; automatic updates tofriends and family; digital and viral gifts, such as baby images withdigital lullabies; invites and thank you cards; etc.

A user can be charged a fee for setting up an account, e.g., asubscription fee, either one time or periodic, the user and family andfriends can also be charged for the various products and services, orboth.

In addition, kiosks 908 can be set up, e.g., in maternity wards that canprovide at least some of the same services. Kiosk 908 can either bestand alone, i.e., interfaced directly with CCS 30, or can be interfacedwith server 902 as illustrated. Thus, family and friends can orderpictures and other goods, e.g., right in the waiting room.

Further, the user can continue to use the account even after the birthof the child. For example, the site can track the child throughout itschild hood, or at least through the first few months or years. The sitecan be configured to send birthday reminders and announcements tofriends and family or to inform of other special events, developmentalmilestones, etc. Moreover, the site can be configured to continue topresent developmental information as well as health and nutrition tipsfor both mother and child.

In fact, it can be preferable to have the parent upload contactinformation for friends and family. In this manner, server 902 can beconfigured to continue to send birthday reminders to friends and family.In certain embodiments, the site hosted by server 902 can be affiliatedwith or host a “gift store” offering various products and services.Alternatively, or in addition, the site can offer discounts, coupons,etc., to various other business and stores. Since server 902 will havepertinent demographic information related to the child, e.g., residenceinformation, sex, age, race, and possibly even parents age, profession,and other affiliations, the site can send reminders, giftrecommendations, discount offers, etc., that are appropriate for thechild and the family, popular with similar demographics, etc.

In this regard, it can be preferable to offer the user the opportunityto provide such demographic information. Thus, in one embodiment, theuser can access the site and customize or provide profile information,contacts, preferences, etc. Algorithms running on server 902 can beconfigured to then use the information available to make productrecommendations, etc. In fact, since server 902 will have informationfor individuals all over the world, the algorithms can be configured touse information for populations that share similar demographics, incomelevels, preferences, etc., to make recommendations.

In certain embodiments, a user can purchase items through the site,i.e., through server 902. For example, server 902 can be configured toaccept credit card payment, a PayPal account, or for mobile billing.Thus, server 902 can be configured to process the transaction and eitherdeduct an appropriate fee or charge a related business, affiliate,partner, etc., a transaction fee. Moreover, purchase information canalso be fed into the algorithms and used to make future recommendations.In fact, the purchases of an entire related population can be used tomake more targeted and appropriate recommendations.

Thus, as a child grows, the algorithms can be constantly updated andhoned in order to make, e.g., gift recommendations. Recommendations thatcan be automatically sent out to friends and family over the years. Asthe database grows over time and with more and more users, thealgorithms can be honed to provide ever more relevant and targetedrecommendations.

It should also be noted that the database will necessarily include vastinformation about the relationships and connections between a largepopulation. This includes direct links such as friends and family, butalso more indirect links such as preferences, similar buying habits,etc. This type of interconnection information can be very valuable fortargeted advertising and product recommendations as well as for simplytracking and mapping the interconnectedness of a large population.

It should be pointed out that such a site can be built around otherconditions or events, such as a cancer support site, physical therapysupport site, etc. It should also be pointed out that the merging ofinterconnectedness data for these various other conditions and eventscan extend the power of the information and lead to even betteralgorithms for targeting information and products and services.

It should also be noted that users can access the site via, e.g., theInternet using computers 914 and mobile devices 912. Further, the sitecan be interfaced with other social networking sites such as Twitter,Facebook, etc. In certain embodiments, the site can actually beconverted to an application, or widget that can be exported to othersites. For example, a grandma can place the application on her Facebookpage and receive updates and notices more easily without needing to logonto server 902. This can increase the interaction with the site, whichcan increase, for example, the amount of information and data availableto server 902 as input to the algorithms described above.

While certain embodiments have been described above, it will beunderstood that the embodiments described are by way of example only.Accordingly, the systems and methods described herein should not belimited based on the described embodiments. Rather, the systems andmethods described herein should only be limited in light of the claimsthat follow when taken in conjunction with the above description andaccompanying drawings.

What is claimed:
 1. A system for automated conversion and delivery of medical images, comprising: a communication interface; a user interface at a source modality, wherein the source modality is an ultrasound machine; a data storage system configured to store: a plurality of medical images, meta data associated with the plurality of medical images, converted medical images, wherein the converted medical images being different from the plurality of medical images, a plurality of standardized format specifications for a plurality of destination devices and services, and a plurality of message templates; a server coupled with the data storage system, the user interface at the source modality and the communication interface, the server configured to: receive a plurality of source medical image files via the communications interface, the source medical image files comprising medical data and meta data, the medical data having a medical data format; store the medical image files in the data storage system; receive a request via the user interface at the source modality to find a particular medical image file; return a notification that the requested medical image file has been found via the user interface; receive a destination address for the found medical image file from the user interface at the source modality; determine an output destination type from meta data associated with the found medical image file, wherein the output destination type is an output device, service, or both, and is associated with the received destination address; retrieve the found medical image file from the data storage system; determine whether medical data associated with the found medical image file includes medical image data; in response to determining that the medical data associated with the requested medical image file includes medical image data: identify at least one standardized format specification from the plurality of standardized format specifications and at least one message template from the plurality of message templates based on the determined output destination type; convert the medical data into a format compatible with the at least one standardized format specification of the output destination type; assemble the converted medical data into at least one output message based on the at least one message template; and transmit the at least one output message to the destination address via the communication interface.
 2. The system of claim 1, wherein the meta data associated with the found medical image file includes information identifying a device used to capture the medical data.
 3. The system of claim 1, wherein the meta data associated with the found medical image file includes information identifying an operator associated with the capture of the medical data.
 4. The system of claim 1, wherein the meta data associated with the found medical image file includes information identifying a time and date the medical data was captured.
 5. The system of claim 1, wherein the meta data associated with the found medical image file includes information identifying at least one of a series and a study associated with the medical data.
 6. The system of claim 1, further comprising storing the found medical image file, wherein the storing comprises correlating the found medical image file with patient information obtained from the meta data, and then storing the found medical image file with links to the patient information.
 7. The system of claim 6, wherein the patient information comprises a name.
 8. The system of claim 6, wherein the patient information comprises a birth date.
 9. The system of claim 6, wherein the patient information comprises a patient identifier.
 10. The system of claim 6, wherein the patient information comprises an address.
 11. The system of claim 6, wherein the patient information comprises an address associated with the determined output destination type.
 12. The system of claim 6, wherein the patient information comprises an address associated with a plurality of output destination types.
 13. The system of claim 6, wherein the request includes patient information and wherein the server is further configured to use the included patient information to locate the requested medical image file.
 14. The system of claim 1, wherein the communication interface comprises a plurality of output gateways, and wherein the server is further configured to identify at least one output gateway based on the determined destination type and to transmit the at least one output message via the at least one output gateway.
 15. The system of claim 14, wherein the output destination type is a mobile device.
 16. The system of claim 14, wherein the output destination type is an e-mail account.
 17. The system of claim 14, wherein the output destination type is a web site that comprises an Application Specific Interface (API) for communicating with the website, and wherein the associated standardized format specification and message template of the web site is based on the API.
 18. The system of claim 1, wherein at least some of the meta data associated with the found medical image file is included in a header portion of the found medical image file.
 19. The system of claim 1, further configured to store the converted medical data at least temporarily.
 20. The system of claim 1, wherein the storing the medical image files comprises storing the medical image content and at least some of the meta data associated with each of the medical image files.
 21. The system of claim 1, wherein the server is further configured to identify a modality associated with the medical data based on the meta data of the found medical image file.
 22. The server of claim 1, wherein the server is further configured to identify specific characteristics of the medical data and extracting the medical data of the found medical image file.
 23. The system of claim 22, wherein the identifying specific characteristics of the medical data comprises determining whether the medical data includes reports, measurements, or both, and wherein the server is further configured to extract the medical data, convert it into a generic structured format, and store the medical data in the generic structured format when it is determined that the medical data includes reports, measurements, or both.
 24. The system of claim 22, wherein the identifying specific characteristics of the medical data comprises identifying at least one of the binary encoding format, frame size, color bit depth, and whether the medical data includes still images or video images, when it is determined that the medical data includes medical image data.
 25. The system of claim 1, wherein the storage system is further configured to store destination specific information for the plurality of destination devices or services, and wherein the server is further configured to convert the medical data associated with the found medical image file into a medical data format based on the destination specific information.
 26. The system of claim 25, wherein the destination specific information includes capabilities of the destination device or service, physical characteristics of the destination device or service, limitations associated with a network class associated with the destination device or service, and limitations associated with a message type associated with the destination device or service.
 27. The system of claim 25, wherein the destination specific information includes at least one of a frame size, data rate, data size, and supported encoding format.
 28. The system of claim 1, wherein the medical data is not converted when the at least one standardized format specification indicates that the destination type is compatible with the medial data format.
 29. The system of claim 1, wherein the output message includes the converted medical data and additional data.
 30. The system of claim 29, wherein the additional data is manually entered via another user interface coupled with the server, extracted from the meta data, or both.
 31. The system of claim 1, wherein the storage system is further configured to store anonymization rules, and wherein the server is further configured to modify the medical data associated with the found medical image file based on the anonymization rules when required before assembling the output message.
 32. The system of claim 1, wherein the medical data format associated with the found medical image file complies with the digital imaging and communication in medicine standard.
 33. A method of automated conversion and delivery of ultrasound images, the method comprising steps of: receiving, at a server, a plurality of source medical image files via the communications interface, the source medical image files comprising medical data and meta data, the medical data having a medical data format; storing the medical image files in a data storage system coupled to the server; receiving, at the server, a request via a user interface at a source modality to find a medical image file, wherein the source modality is an ultrasound machine and the requested image being at least one ultrasound image; returning, by the server, a notification that the requested medical image file has been found via the user interface; receiving, at the server, a destination address for the found medical image file from the user interface at the source modality; determining, by the server, an output destination type from meta data associated with the found medical image file, wherein the output destination type is an output device, service, or both, and is associated with the received destination address; retrieving, by the server, the found medical image file from the data storage system; determining, at the server, whether medical data associated with the found medical image file includes medical image data; in response to determining that the medical data associated with the found medical image file includes medical image data, the server further implements: identifying at least one standardized format specification from a plurality of standardized format specifications stored at the data storage system and at least one message template from the plurality of message templates stored at the data storage system based on the determined output destination type; converting the medical data into a format compatible with the at least one standardized format specification of the output destination type; assembling the converted medical data into at least one output message based on the at least one message template; and transmitting the at least one output message to the destination address via the communication interface.
 34. The method of claim 33, further comprising first requesting transmission of the at least one ultrasound image from the ultrasound machine at the user interface on the ultrasound machine.
 35. The method of claim 33, wherein the at least one ultrasound image is transmitted from the ultrasound machine to the server through a communications interface connected with the ultrasound machine.
 36. The method of claim 33, wherein the output destination type is a social networking website.
 37. The method of claim 36, wherein the output destination type includes the image format which the ultrasound image to be converted to for displaying on the social networking website.
 38. The method of claim 37, wherein the converted at least one ultrasound image is transmitted to one or more users of the social networking website.
 39. The method of claim 33, wherein the output destination type is an e-mail account.
 40. The method of claim 39, wherein the output destination type includes the image format which the ultrasound image to be converted to for displaying in an e-mail.
 41. The method of claim 40, wherein the converted at least one ultrasound image is transmitted to one or more e-mail addresses. 